…mass M to m_cart and cart pole mass m to m_pole

added comments about meaning of "stage" in MPPI
renamed TargetPositionGenerator to TargetTrajectoryGenerator, since we target a complete trajectory, not just cart position.
renamed my_logger() to get_logger()

say which compiler we are using

…istency with other config files.

added more docstrings for undocumented methods and constructors.
added updated_attributes to barebones controller.
improved formatting of logging output
added dictdiffer to requirements.txt
renamed target_position cost function to cartpole_trajectory_cost.py.
replaced some load_config with the load_or_reload_config_if_modified, so that the configs are cached for change checking.
added logger to Compile.py

…g and the cartpole is at least balancing itself and swinging up from down position. Big changes all over!

Now anytime any of the config files is modified during runtime, the using class has its tf.variable assigned the new value.
To get this work, the variable MUST NOT EXIST before it is set this way the first time. Otherwise the compiler just uses the field at compile time and the changes are never seen inside.
The cartpole window now does not reset the initial position and angle sliders on each start.

…hanging the cost weights during runtime! Yay, finally!

Trick was to make sure that all values are actually propagated to tf variables, e.g. numpy arrays, ints, string, not just float

Changed logging format to start with level for better readability.
added string type to computation_library.py

# Conflicts:
#	src/SI_Toolkit/computation_library.py

added prefs to cartpole gui for initial position and angle
increased num_rollouts to 1000, decreased horizon to 25 time steps, changed cost function for spin to pure cart angle speed. Now spin, balance, and shimmy all work quite well.
moved cartpole_trajectory_generator back out outside compiled TF code for ease of development and debugging, it is cheap so this is OK.
added more logging of what gets compiled.
added time to arguments for the base controller so that contained methods can access current time.
added ruamel.yaml to requirements (this is the yaml parser that can handle scientific notation numbers)

# Conflicts:
#	Control_Toolkit_ASF_Template/Cost_Functions/EnvironmentName/cost_function_barebone.py
#	Control_Toolkit_ASF_Template/config_optimizers.yml
#	Controllers/__init__.py
#	Controllers/controller_neural_imitator_tf.py
#	Cost_Functions/__init__.py
#	Cost_Functions/cost_function_wrapper.py
#	Optimizers/optimizer_mppi.py
#	Optimizers/optimizer_rpgd_me_tf.py
#	Optimizers/optimizer_rpgd_ml_tf.py
#	Optimizers/optimizer_rpgd_particle_tf.py
#	Optimizers/optimizer_rpgd_tf.py
#	requirements.txt

# Conflicts:
#	src/SI_Toolkit/Predictors/predictor_wrapper.py

Started merging from remote/origin/Tobi_Dance

…cal-cartpole repo. Fix some cartpole parameter import. Fix rename of config_cost_functions.yml. Add timer.py and yes_or_no.py utility classes.

… seem to work. mppi parameters copied from development. cost weights adjusted.

controller update interval inccreased to 25ms from 20ms to match simulator and actual achieved rate with dancer mppi.
mppi rollouts reduced to 700 to speed up control.
PhysicalCartPoleDriver.py has class self variable for reference from other classes to the instance.
Compile.py raises exception when either option is undefined.

… for next timestep and recording this prediction along with the measurement in the PhysicalCartPoleDriver.py CSV output file. In this commit, control is enabled by default because the pycharm debugger hangs on interactive terminal keyboard intput, and the motor output is disabled for remote debugging.

commented out some noisy log.debug.
made horizon same as physical cartpole

updated satisfaction CSV to use markers from audition and added more cartsheels

…or for compatibilty with RPGD gradient computation.

update_attributes in globals_and_utils.py supports assignment of tf.Variable and now raises exception if we try to .assign an immutable Tensor.
Balance step now uses int +1 or -1 for desired pole up or down, not 'up' or 'down'.
computation_library.py now casts variale to numpy() from tensorflow only if it is a Tensor type.